This repository was archived by the owner on Nov 10, 2021. It is now read-only.
Simple feed / featured / ban list caching #31
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
feat: feed caching at 1 minute instead of 10 seconds as this is likely the update time of the blockchain
Collaborator
|
Nice, merging! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implemented simple caching that lasts 1 minute for:
This is a temporary fix to speed the site up before a rewrite. It should both minimize load times on the feed and make the Lambdas less expensive to run.
Also note this could be implemented for the hDAO feed as well.
Implementing for random would need caching of the
getUniversecall which is a whole different thing and should wait until a rewrite is complete. That said, it could be easy to implement a set of randoms ie have a bucket of 10 random caches that can only be updated once a minute. On each request show data from one of these caches, unless it has expired. This way you could click random a few times a minute and it would still be fast.